Work around K3s pod-resources socket flake - #482
Open
dajudge wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Mount
/var/lib/kubelet/pod-resourcesas tmpfs inK3sContainer.Why
K3s can occasionally fail kubelet startup with:
failed to move temporary file to addr "/var/lib/kubelet/pod-resources/kubelet.sock": ... invalid cross-device linkThis is the same failure tracked upstream in k3s-io/k3s#4042. Keeping the pod-resources socket directory on a dedicated tmpfs avoids the overlay/filesystem boundary involved in the failing rename without moving broader K3s or kubelet state into memory.
Impact
The change is intentionally narrow: only the kubelet pod-resources runtime socket directory is affected. Existing
/runand/var/runtmpfs mounts remain unchanged.